Welcome Guest, you are in: Login
CTS Futures

Page History: Standard Header

Compare Page Revisions



« Older Revision - Back to Page History - Newer Revision »


Page Revision: 2012/09/05 17:49


All messages (administrative or application) are preceded by a Standard Header. In addition to providing the identification of FIX Session participants, the Standard Header identifies the Message Type (Tag 35), Message Length (Tag 9), Origination times (Tag 52 and Tag 122) and Message Sequence order (Tag 34). The Standard Header also offers additional information on FIX Session authentication, resent messages, duplicated message and message routing and delivery.

Standard Message Header

agField NameReq'dComments
BeginString YFIX.4.2 (Always unencrypted, must be first field in message)
BodyLengthY(Always unencrypted, must be second field in message)
5MsgTypeY(Always unencrypted, must be third field in message)
9SenderCompIDY(Always unencrypted)
6TargetCompIDY(Always unencrypted)
15OnBehalfOfCompIDNTrading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)
28DeliverToCompIDNTrading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)
0SecureDataLenNRequired to identify length of encrypted section of message. (Always unencrypted)
1SecureDataNRequired when message body is encrypted. Always immediately follows SecureDataLen field.
4MsgSeqNumY(Can be embedded within encrypted data section.)
0SenderSubIDN(Can be embedded within encrypted data section.)
42SenderLocationIDNSender's LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)
7TargetSubIDN“ADMIN” reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.)
43TargetLocationIDNTrading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)
16OnBehalfOfSubIDNTrading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)
44OnBehalfOfLocationIDNTrading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)
29DeliverToSubIDNTrading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)
45DeliverToLocationIDNTrading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)
3PossDupFlagNAlways required for retransmitted messages, whether prompted by the sending system or as the result of a resend request. (Can be embedded within encrypted data section.)|
7PossResendNRequired when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.)
2SendingTimeY(Can be embedded within encrypted data section.)
22OrigSendingTimeNRequired for message resent as a result of a ResendRequest. If data is not available set to same value as SendingTime (Can be embedded within encrypted data section.)
12XmlDataLenNRequired when specifying XmlData to identify the length of a XmlData message block. (Can be embedded within encrypted data section.)
13XmlDataNCan contain a XML formatted message block (e.g. FIXML). Always immediately follows XmlDataLen field. (Can be embedded within encrypted data section.)
47MessageEncodingNType of message encoding (non-ASCII characters) used in a message’s “Encoded” fields. Required if any “Encoding” fields are used.
69LastMsgSeqNumProcessedNThe last MsgSeqNum value received by the FIX engine and processed by downstream application, such as trading system or order routing system. Can be specified on every message sent. Useful for detecting a backlog with a counterparty.
27NoHopsNNumber of repeating groups of historical “hop” information. Only applicable if OnBehalfOfCompID is used, however, its use is optional. Note that some market regulations or counterparties may require tracking of message hops.
28HopCompID GroupNThird party firm which delivered a specific message either from the firm which originated the message or from another third party (if multiple “hops” are performed). It is recommended that this value be the SenderCompID (49) of the third party.
29HopSendingTimeNTime that HopCompID (628) sent the message. It is recommended that this value be the SendingTime (52) of the message sent by the third party.
30HopRefIDNReference identifier assigned by HopCompID (628) associated with the message sent. It is recommended that this value be the MsgSeqNum (34) of the message sent by the third party.

FIX API Home Page.





Trade how you want, where you want

support@ctsfutures.com (312) 939 0164

2 Pierce Pl, Suite 200, Itasca, IL 60143

© 2009-2023 Cunningham Trading Systems LLC All rights reserved.